Network sharing and reverse single radio voice call continuity

ABSTRACT

Certain networks can operate using circuit switched infrastructure, while other networks may operate using infrastructure for the long term evolution (LTE) of the third generation partnership project (3GPP). Devices can operate across the boundaries of these networks. Thus, such devices as well as the networks may benefit from network sharing in reverse single radio voice call continuity. For example, a method may include requesting handover of a user equipment from a source network to a target network. The method may also include providing a network identification corresponding to the source network while requesting the handover. Alternatively, or in addition, a method may include requesting handover of a user equipment from a source network to a target network. The method may also include determining the target network based on a network identification received previously.

BACKGROUND

1. Field

Certain networks can operate using circuit switched infrastructure,while other networks may operate using infrastructure for the long termevolution (LTE) of the third generation partnership project (3GPP).Devices can operate across the boundaries of these networks. Thus, suchdevices as well as the networks may benefit from network sharing inreverse single radio voice call continuity.

Certain networks can also operate using circuit switched infrastructureitself with multiple operators. Devices can operate across theboundaries of multiple operators' covered areas within these networks.Thus, such devices as well as the networks may benefit from networksharing while maintaining voice call continuity between or amongoperators' covered areas.

2. Description of the Related Art

In Release 8 (Rel 8), 3GPP specified single radio voice call continuity(SRVCC) from LTE to second or third generation (2/3G) circuit switched(CS). SRVCC can refer to the procedures for continuity and alternativelycan also be used to describe the action of using such procedures. In Rel11, 3GPP specified SRVCC in the 2/3G CS to LTE packet switched (PS)direction, namely reverse SRVCC (rSRVCC). Network sharing with behaviorfor handover target selection from LTE to 2/3G CS is described in 3GPPtechnical specification (TS) 23.251, which is incorporated herein byreference in its entirety. However, network sharing behavior forhandover from CS domain to LTE has not been defined in 3GPP.

Network sharing behavior for handover from CS domain to another CSdomain is described in 3GPP TS 23.251.

SUMMARY

According to a first embodiment, a method may comprise requestinghandover of a user equipment from a source network to a target network.The method may also comprise providing a network identificationcorresponding to the source network while requesting the handover.

In the first embodiments, the source network may be a packet-switchednetwork and the target network may be a circuit switched network.

The network identification, in the first embodiments, may be anidentification of a current public land mobile network in use (forexample an identification of a public land mobile network used when thecall or session is first established or used after a packet switched topacket switched handover) or a source public land mobile networkidentifier.

According to the first embodiment, the handover request may be a packetswitched to circuit switched handover request comprising the networkidentification.

The handover request, according to the first embodiment, may be a singleradio voice call continuity request from a packet switched network to acircuit switched network.

In the first embodiment, the requesting the handover may be performed bya mobility management entity or serving general packet radio servicesupport node and the identification may be provided to a mobileswitching center.

The source network, in a variation of the first embodiment, may be acircuit switched network and the target network may be a circuitswitched network.

The network identification, according to the variation of the firstembodiment, may comprise an identification of a circuit switched publicland mobile network used (for example an identification of a public landmobile network used when the call is first established or used after apacket switched to packet switched hand over) or a source circuitswitched public land mobile network identifier.

The handover request may be a circuit switched handover requestcomprising the network identification in the variation of the firstembodiment.

The handover request may be a circuit switched handover request from onecircuit switched radio access technology to another circuit switchedradio access technology or from one circuit switched network to anothercircuit switched network, according to the variation of the firstembodiment.

According to the variation of the first embodiment, handover may berequested by the source network and identification may be provided tothe target network.

In a second embodiment, the method may comprise requesting handover of auser equipment from a source network to a target network. The method mayalso comprise determining the target network based on a networkidentification received previously.

The source network, in the second embodiment, may be a circuit switchednetwork and the target network may be a packet switched network.

According to the second embodiment, the network identification maycomprise a source public land mobile network identification from thepacket switched network (for example received from the packet switchednetwork), or a target public land mobile network identifier.

The handover request may be, in the second embodiment, a circuitswitched to packet switched handover request comprising the networkidentification.

In the second embodiment, the handover may be a reverse single radiovoice call continuity handover.

According to the second embodiment, the handover request may betransmitted from a base station controller or radio network controllerto a mobile switching center.

The network identification, in the second embodiment, might have beenreceived with an earlier packet switched to circuit switched handoverrequest and might be a network identification of an earlier used sourcepacket switched public land mobile network.

A method, according to a third embodiment, may comprise requestinghandover of a user equipment from a source network to a target network.The method may also comprise forwarding a network identificationreceived previously at the source network to the target network.

In the third embodiment, the source network may be a circuit switchednetwork and the target network may be a circuit switched network.

According to the third embodiment, the handover request may be aninter-radio access technologies handover request or an intra-radioaccess technology handover request.

The handover request may comprise the network identifier in a thirdembodiment.

The handover request, according to the third embodiment, may betransmitted from a source base station controller or source radionetwork controller to a target base station controller or a target radionetwork controller.

The network identification, in the third embodiment, may be a sourcepublic land mobile network identification from a packet switchednetwork, which might have been received with an earlier packet switchedto circuit switched handover request and might be a networkidentification of the earlier source packet switched network or anetwork identifier of the earlier source packet switched network.

According to the third embodiment, the network identification may be asource public land mobile network identification from a circuit switchednetwork, which might have been received with an earlier circuit switchedto circuit switched handover request and might be a networkidentification of the earlier source circuit switched network or anetwork identifier of the earlier source circuit switched network.

A method, in a fourth embodiment, may comprise receiving a request forhandover of a user equipment from a source network to a target network.The method may also comprise forwarding a network identificationcorresponding to the source network to the target network.

In the fourth embodiment, the source network may be a packet switchednetwork and the target network may be a circuit switched network.

According to the fourth embodiment, the network identification maycomprise a current packet switched public land mobile network in useinformation or a source packet switched public land mobile networkidentifier.

The handover request, in the fourth embodiment, may be a packet switchedto circuit switched handover request comprising the networkidentification.

The handover request may be a reverse single radio voice call continuityhandover request, according to the fourth embodiment.

The handover request, in the fourth embodiment, may be received from amobility management entity or serving general packet radio servicesupport node and may be forwarded to a base station controller or radionetwork controller.

A non-transitory computer-readable medium is, in a fifth embodiment,encoded with instructions that, when executed in hardware, perform aprocess. The process may comprise requesting handover of a userequipment from a source network to a target network. The process alsomay comprise providing a network identification corresponding to thesource network while requesting the handover. The process may alsoencompass all the variations of the method of the first embodiment,described above.

A non-transitory computer-readable medium is, according to a sixthembodiment, encoded with instructions that, when executed in hardware,perform a process. The process may comprise requesting handover of auser equipment from a source network to a target network. The processmay also comprise determining the target network based on a networkidentification received previously. The process may also encompass allthe variations of the method of the second embodiment, described above.

In a seventh embodiment, a non-transitory computer-readable medium isencoded with instructions that, when executed in hardware, perform aprocess. The process may comprise requesting handover of a userequipment from a source network to a target network. The process mayalso comprise forwarding a network identification received previously atthe source network to the target network. The process may also encompassall the variations of the method of the third embodiment, describedabove.

According to eighth embodiment, a non-transitory computer-readablemedium is encoded with instructions that, when executed in hardware,perform a process. The process may comprise receiving a request forhandover of a user equipment from a source network to a target network.The process may also comprise forwarding a network identificationcorresponding to the source network to the target network. The processmay also encompass all the variations of the method of the fourthembodiment, described above.

In a ninth embodiment, an apparatus may comprise at least one processorand at least one memory comprising computer program code. The at leastone memory and the computer program code may be configured to, with theat least one processor, cause the apparatus at least to request handoverof a user equipment from a source network to a target network. The atleast one memory and the computer program code may be also configuredto, with the at least one processor, cause the apparatus at least toprovide a network identification corresponding to the source networkwhile requesting the handover. The apparatus may be configured toperform all the variations of the method of the first embodiment,described above.

The apparatus, in the ninth embodiment, may be a mobility managemententity or a mobile switching center.

According to a tenth embodiment, an apparatus may comprise at least oneprocessor and at least one memory comprising computer program code. Theat least one memory and the computer program code may be configured to,with the at least one processor, cause the apparatus at least to requesthandover of a user equipment from a source network to a target network.The at least one memory and the computer program code may be alsoconfigured to, with the at least one processor, cause the apparatus atleast to determine the target network based on a network identificationreceived previously. The apparatus may be configured to perform all thevariations of the method of the second embodiment, described above.

In the tenth embodiments, the apparatus may be a base station controlleror a radio network controller.

An apparatus, in an eleventh embodiment, may comprise at least oneprocessor and at least one memory comprising computer program code. Theat least one memory and the computer program code may be configured to,with the at least one processor, cause the apparatus at least to requesthandover of a user equipment from a source network to a target network.The at least one memory and the computer program code may be alsoconfigured to, with the at least one processor, cause the apparatus atleast to forward a network identification received previously at thesource network to the target network. The apparatus may be configured toperform all the variations of the method of the third embodiment,described above.

According to eleventh embodiment, the apparatus may be a base stationcontroller, a radio network controller, or a mobile switching center.

An apparatus, according to a twelfth embodiment, may comprise at leastone processor and at least one memory comprising computer program code.The at least one memory and the computer program code may be configuredto, with the at least one processor, cause the apparatus at least toreceive a request for handover of a user equipment from a source networkto a target network. The at least one memory and the computer programcode may be also configured to, with the at least one processor, causethe apparatus at least to forward a network identification correspondingto the source network to the target network. The apparatus may beconfigured to perform all the variations of the method of the fourthembodiment, described above.

The apparatus may comprise a mobile switching center, according tocertain embodiments.

In a thirteenth embodiment, an apparatus may comprise requesting meansfor requesting handover of a user equipment from a source network to atarget network. The apparatus may also comprise providing means forproviding a network identification corresponding to the source networkwhile requesting the handover. The apparatus may also comprise means forperforming all the variations of the method of the first embodiment,described above.

According to fourteenth embodiment, an apparatus may comprise requestingmeans for requesting handover of a user equipment from a source networkto a target network. The apparatus may also comprise determining meansfor determining the target network based on a network identificationreceived previously. The apparatus may also comprise means forperforming all the variations of the method of the second embodiment,described above.

An apparatus, in fifteenth embodiment, may comprise requesting means forrequesting handover of a user equipment from a source network to atarget network. The apparatus may also comprise forwarding means forforwarding a network identification received previously at the sourcenetwork to the target network. The apparatus may also comprise means forperforming all the variations of the method of the third embodiment,described above.

An apparatus, according to a sixteenth embodiment, may comprisereceiving means for receiving a request for handover of a user equipmentfrom a source network to a target network. The apparatus may alsocomprise forwarding means for forwarding a network identificationcorresponding to the source network to the target network. The apparatusmay also comprise means for performing all the variations of the methodof the fourth embodiment, described above.

A system, in a seventeenth embodiment, may comprise a first apparatuscomprising at least one processor and at least one memory comprisingcomputer program code, wherein at the at least one memory and thecomputer program code are configured to, with the at least oneprocessor, cause the first apparatus at least to request first handoverof a user equipment from a first source network to a first targetnetwork and provide a network identification corresponding to the firstsource network while requesting the handover. The system may alsocomprise a second apparatus comprising at least one processor and atleast one memory comprising computer program code, wherein at the atleast one memory and the computer program code are configured to, withthe at least one processor, cause the second apparatus at least torequest handover of the user equipment from a second source network to asecond target network and forward the network identification receivedpreviously from the first apparatus at the source network to the targetnetwork, wherein the second source network corresponds to the firsttarget network. The system may further comprise a third apparatuscomprising at least one processor and at least one memory comprisingcomputer program code, wherein at the at least one memory and thecomputer program code are configured to, with the at least oneprocessor, cause the third apparatus at least to receive the requestfrom the second apparatus for handover of the user equipment from thesecond source network to the second target network and forward thenetwork identification corresponding to the source network to the targetnetwork. The system may additionally comprise a fourth apparatuscomprising at least one processor and at least one memory comprisingcomputer program code, wherein at the at least one memory and thecomputer program code are configured to, with the at least oneprocessor, cause the fourth apparatus at least to request handover ofthe user equipment from a third source network to a third target networkand determine the third target network based on the networkidentification received previously, wherein the third source networkcorresponds the second target network.

The first, second, third, and fourth apparatuses in the system of thethirteenth embodiment may be configured to perform all the variations ofthe methods of the first, second, third, and fourth embodiments,described above.

BRIEF DESCRIPTION OF THE DRAWINGS

For proper understanding of the invention, reference should be made tothe accompanying drawings, wherein:

FIG. 1 illustrates possible network-sharing scenarios.

FIG. 2 illustrates the sharing of a circuit switched public land mobilenetwork by two long term evolution mobile networks, according to certainembodiments.

FIG. 3A illustrates a signaling flow according to certain embodiments.

FIG. 3B illustrates a signaling flow according to certain embodiments.

FIG. 4 illustrates a method according to certain embodiments.

FIG. 5A illustrates a system according to certain embodiments.

FIG. 5B illustrates a system according to certain embodiments.

DETAILED DESCRIPTION

FIG. 1 illustrates possible network-sharing scenarios. In the sharingscenarios, the circuit switched (CS) domain 110 may be configured withMobile Operator Core Network (MOCN) sharing models (lower left side ofFIG. 1) and Gateway Core Network (GWCN) sharing model (lower right sideof FIG. 1). On the long term evolution (LTE) side 120, the network maybe configured similarly: upper left of FIG. 1 shows MOCN, upper right ofFIG. 1 shows GWCN models. The connection between the LTE and CS domainmay be the Sv interface, which is defined in 3GPP.

FIG. 1 more particularly illustrates several CN Operators respectivelyCN Operator A 111 a, CN Operator B 111 b, and CN Operator C 111 c. Thefigure also illustrates shared MSC/SGSNs 112 a, 112 b, and 112 c. Thefigure further illustrates a radio access network (RAN) belonging tooperator X 113. In the RAN one may find one or more radio networkcontrollers (RNCs) 114. All these may be found on the CS domain side110.

On the packet switched domain side 120, there is illustrated an evolvedpacket core element 121, connected to a eNode B (eNB) 122, which isserving a cell 123 and a user equipment 124. The operator networks 125can specifically comprise such elements as S-GW 126 and MME 127.

As mentioned above, network sharing behavior from CS domain to LTE hasnot been defined in 3GPP. In particular, the scenario illustrated inFIG. 2 is not conventionally addressed.

FIG. 2 illustrates the sharing of a circuit switched public land mobilenetwork by two long term evolution mobile networks, according to certainembodiments. More particularly, FIG. 2 shows that the serving area maycomprise two LTE PLMNs, LTE-PLMN A 210 and LTE-PLMN B 220, and they bothmay use the same CS PLMN-CS 230 for single radio voice call continuity(SRVCC). This may be viewed as two green field LTE operators relaying on3rd party CS Domain for SRVCC. A Venn diagram illustrates the sharing attop, while a network connection view is shown at the bottom of FIG. 2.

The two LTE networks 210 and 220 can comprise respect MMEs 211 and 221,respective E-UTRANs 212 and 222, respective S-GWs 213 and 223,respective PGWs 214 and 224, and respective IMSs 215 and 225. Alsoillustrated is the CS RAN/BSS 235 connected to the PLMN-CS (MSS) 230.

In one case, a user equipment (UE) may start an internet protocol (IP)multimedia subsystem (IMS) voice session with PLMN-A and SRVCC over toPLMN-CS. The source evolved universal terrestrial radio access network(E-UTRAN) may select the “target CS PLMN” and may send this selected“target CS PLMN” in a message to the PLMN-CS's MSS via Sv for targetresource handling. When this call is returned, going back from CS to LTEwith rSRVCC, the CS radio node, such as for example a BTS or NodeB, canselect the target LTE PLMN based on a current PLMN in use. This maystill be the selected “CS PLMN”. This “CS PLMN” may perform rSRVCC toeither LTE-PLMN-A or LTE-PLMN-B.

If a wrong LTE-PLMN is selected, the result may be rSRVCC failure if,for example, the radio node decided to use LTE-PLMN-B but LTE-PLMN-B andLTE-PLMN-A do not have roaming agreement. This may be because theserving gateway (S-GW) in the PLMN-B cannot establish an S5 connectionwith the proxy gateway (P-GW) in PLMN-A or the MME in the PLMN-B cannotestablish an S10 connection with the MME in PLMN-A. The S5 and S10connections are shown with dotted lines in FIG. 2. In other words, inthis example for rSRVCC to work, the P-GW established prior to rSRVCCmust be the anchor point also after rSRVCC, and the new MME (B) must beable to retrieve the user equipment (UE) Packet Switch user informationfrom old MME (A).

Moreover, even if the rSRVCC may be successful because LTE-PLMN-A andLTE-PLMN-B have a roaming agreement, the result may be a roaming S5unnecessarily being established, when the call could have been handledin LTE-PLMN-A directly. This may also lead to unnecessary roamingcharges because an additional PLMN is involved.

Certain embodiments provide a way by which the radio node, such as forexample a BTS or NodeB, can decide which PLMN (A or B) to use for targetLTE selection. FIG. 3A illustrates a signaling flow according to certainembodiments.

As shown in FIG. 3A, when the call may be first SRVCC from LTE to CS atB1, the source LTE PLMN-ID may be carried to MSS via Sv interface in PSto CS handover request message at B2.

At B3, if the CS PLMN supports rSRVCC, the MSS may also indicate this“source LTE PLMN-ID” to target BSS/RAN. Moreover, at B4 and B5, the restof the SRVCC procedure may be executed and the UE may be now served byCS RAT. The voice call may be continuing in CS Domain.

If there may be an inter/intra CS RATs handover, the source BSS/RAN mayforward the “source LTE PLMN-ID” to the target BSS/RAN. This is notshown in FIG. 3A.

At B6, when the current serving CS RAT may need to perform rSRVCC targetselection, it may use the “source LTE PLMN-ID” as one of the input fortarget LTE selection to ensure the selected PLMN will not result in afail call. Thus, the current serving CS RAT may select an LTE cell thatbelongs to a source LTE PLMN-ID. Alternatively, the current serving CSRAT may select a roaming partner of the source LTE PLMN as a nextoption. The Neighbor cell list for UE measurement may be also based onthe “source LTE PLMN-ID”.

At B7, the source BSS/RAN may pass the selected target LTE PLMN back tothe MSS to continue the normal rSRVCC procedure.

Thus, in certain embodiments the source LTE PLMN ID may be given to theCS PLMN and it may be passed within the CS PLMN from source to targetduring intra/inter RAT CS handover.

Another aspect of certain embodiments may be that the MSS stores thesource LTE PLMN ID for a further new CS call. This stored source LTEPLMN ID may be updated at the next SRVCC procedure from the Svinterface, if received.

Although the illustration in FIG. 2 is using one CS PLMN with 2 LTEPLMNs, the same approach may be applied to a circuit switched publicland mobile network shared by multiple operators.

In one case, a user equipment (UE) may start a CS call with PLMN-A andget handed over to target PLMN-CS. The source BTS/NodeB may select the“target CS PLMN” and can may comprise this selected “target CS PLMN” ina message to the PLMN-CS's MSS via normal BSS/RAN to MSS signaling, forexample Iu-cs/A, for target resource handling. When this call isreturned, going from PLMN-CS to PLMN-A with normal CS handover, the CSradio node, such as for example a BTS or NodeB, may select the target CSPLMN based on a current PLMN in use. This may still be the selectedPLMN-A or other PLMN-x.

If a wrong PLMN-x is selected, the result may be an additional roamingleg being setup between PLMN-A and PLMN-x which may lead to unnecessaryroaming charges because an additional PLMN is involved.

FIG. 3B illustrates a signaling flow according to certain embodiments.

As shown in FIG. 3B, when the call is first performing CS handover atC1, the source CS PLMN A may be carried to MSS via normal BSS/RAN-MSSsignaling.

At C2 and C3, the anchor MSS may indicate this “source CS PLMN A” totarget BSS/RAN via target MSC. Moreover, at C4 and C5, the rest of theCS handover procedure may be executed and the UE may be now served bytarget CS RAT. The voice call may continue in the CS Domain.

If there is an inter/intra CS RATs handover, the source BSS/RAN mayforward the “source CS PLMN A” to the target BSS/RAN. This is not shownin FIG. 3B.

At C6, when the current serving CS RAT may perform CS handover targetselection, and may use the “source PLMN-A” as one of the inputs fortarget CS selection, to ensure that the selected PLMN will result inoptimized manner, thereby avoiding, for example, any extra roaming legsetup. Thus, the current serving CS RAT may select a target CS cell thatbelongs to a source CS PLMN A. Alternatively, the current serving CS RATmay select a roaming partner of the source CS PLMN as a next option. TheNeighbor cell list for UE measurement may be also based on the “sourceCS PLMN A”.

At C7, the source BSS/RAN may pass the selected target CS PLMN back tothe Anchor MSS to continue the normal CS HO procedure.

Thus, in certain embodiments the source CS PLMN ID may be given to thetarget CS PLMN and may be passed within the target CS PLMN from sourceto target during intra/inter RAT CS handover.

FIG. 4 illustrates a method according to certain embodiments. As shownin FIG. 4, a method may comprise, at 410, requesting handover of a userequipment from a source network to a target network. The method may alsocomprise, at 415, providing a network identification corresponding tothe source network while requesting the handover.

The source network may be a packet-switched or circuit-switched networkand the target network may be a circuit switched network. The networkidentification may comprise an identification of a current public landmobile network in use (for example the public land mobile network usedwhen the call or session is first established) or a source public landmobile network identifier. The handover request may be a packet switchedto circuit switched or circuit switched to circuit switched handoverrequest comprising the network identification. Moreover, the handoverrequest may be a single radio voice call continuity request from apacket switched network to a circuit switched network. The requestingthe handover may be performed for example by a mobility managemententity or serving general packet radio service support node or mobileswitching center and the identification may be provided for example to amobile switching center.

Alternatively, the source network may be a circuit switched network andthe target network may be a circuit switched network. Moreover, thenetwork identification may comprise an identification of a circuitswitched public land mobile network used (for example an identificationof a circuit switched public land mobile network used when the call isfirst established or used after a packet switched to packet switchedhandover) or a source circuit switched public land mobile networkidentifier. The handover request may be a circuit switched handoverrequest comprising the network identification. Furthermore, the handoverrequest may be a circuit switched handover request from one circuitswitched radio access technology to another circuit switched radioaccess technology or from one circuit switched network to anothercircuit switched network. Additionally, the handover may be requested bythe source network and identification may be provided to the targetnetwork.

The method may also comprise, at 420, receiving a request to handover auser equipment from a source network to a target network, and, at 425,passing on that request with a network identification. Passing on therequest may comprise requesting handover of a user equipment from asource network to a target network and forwarding a networkidentification received previously at the source network to the targetnetwork.

The source network may be a circuit switched network and the targetnetwork may be a circuit switched network. The network identificationmay be for example a source public land mobile network identificationfrom a packet switched network, which might have been received with anearlier packet switched to circuit switched handover request and mightbe a network identification of the earlier source packet switchednetwork or a network identifier of the earlier source packet switchednetwork. The handover request may be an inter-radio access technologieshandover request or an intra-radio access technology handover request.Moreover, the handover request may comprise the network identifier.

Alternatively, the handover request may be transmitted from a sourcebase station controller or source radio network controller to a targetbase station controller or a target radio network controller. The sourcenetwork may be a circuit switched network and the target network may bea circuit switched network. The network identification may be a sourcepublic land mobile network identification from a circuit switchednetwork, which might have been received with an earlier circuit switchedto circuit switched handover request and might be a networkidentification of the earlier source circuit switched network or anetwork identifier of the earlier source circuit switched network.

The method may also comprise, at 430, receiving a request for handoverof the user equipment from a source network to a target network. Thisreceiving may comprise recording a network identifier comprised with therequest. The method may further comprise, at 431, requesting handover ofa user equipment from a source network to a target network, for examplein a reverse direction to the previously mentioned handover. The methodmay also comprise, at 433, determining the target network based on anetwork identification received previously.

The source network may be a circuit switched network and the targetnetwork may be a packet switched network. The network identification maybe a source public land mobile network identification from the packetswitched network (for example received from the packet switchednetwork), or a target public land mobile network identifier. Thehandover request may be a circuit switched to packet switched handoverrequest comprising the network identification. For example, the handovermay be a reverse single radio voice call continuity handover. Moreover,the handover request may be transmitted from a base station controlleror radio network controller to a mobile switching station. Moreover, thenetwork identification may be one that was received with an earlierpacket switched to circuit switched handover request and may be anetwork identification of an earlier used source packet switched publicland mobile network.

Furthermore, at 435, the method may comprise receiving a request forhandover of a user equipment from a source network to a target network.The method may also comprise, at 437, forwarding a networkidentification corresponding to the source network to the targetnetwork.

The source network may be a packet switched network and the targetnetwork may be a circuit switched network. More particularly, thenetwork identification may be a current packet switched public landmobile network in use information or a source packet switched publicland mobile network identifier. The handover request may be a packetswitched to circuit switched handover request comprising the networkidentification. The handover request may be a reverse single radio voicecall continuity handover request. Furthermore, the handover request maybe received from a mobility management entity or serving general packetradio service support node and forwarded to a base station controller orradio network controller.

FIG. 5A illustrates a system according to certain embodiments. In anexample embodiment, a system may comprise of several devices, like MME510, MSC 520, and BSC/RNC 530. These devices are merely illustrative ofmany other devices that can be used, such as the devices shown in FIGS.2 and 3. Each of the devices 510, 520, and 530 may be equipped with atleast one processor (respectively 514, 524, and 534), at least onememory (respectively 515, 525, and 535) (comprising computer programinstructions or code), a transceiver (respectively 516, 526, and 536),and an antenna (respectively 517, 527, and 537). There is no requirementthat each of these devices be so equipped. For example, it is notrequired that any of the devices be equipped for wireless communication,but instead may be connected by wired connections.

The transceiver (respectively 516, 526, and 536) may be a transmitter, areceiver, both a transmitter and a receiver, or a unit that isconfigured both for transmission and reception, and can comprise anetwork interface card. The transceiver (respectively 516, 526, and 536)may be coupled to corresponding one or more antenna(s) (respectively517, 527, and 537), or other communications hardware in the case thatantenna(s) are not used.

The at least one processor (respectively 514, 524, and 534) may bevariously embodied by any computational or data processing device, suchas a central processing unit (CPU) or application specific integratedcircuit (ASIC). The at least one processor (respectively 514, 524, and534) may be implemented as one or a plurality of controllers.

The at least one memory (respectively 515, 525, and 535) may be anysuitable storage device, such as a non-transitory computer-readablemedium. For example, a hard disk drive (HDD) or random access memory(RAM) may be used in the at least one memory (respectively 515, 525, and535). The at least one memory (respectively 515, 525, and 535) may be ona same chip as the corresponding at least one processor (respectively514, 524, and 534), or may be separate from the corresponding at leastone processor (respectively 514, 524, and 534).

The computer program instructions may be any suitable form of computerprogram code. For example, the computer program instructions may be acompiled or interpreted computer program.

The at least one memory (respectively 515, 525, and 535) and computerprogram instructions may be configured to, with the at least oneprocessor (respectively 514, 524, and 534), cause a hardware apparatus(for example, MME 510, MSC 520, or BSC/RNC 530) to perform a process,such as any of the processes described herein (see, for example, FIGS. 3and 4).

Thus, in certain embodiments, a non-transitory computer-readable mediummay be encoded with computer instructions that, when executed inhardware perform a process, such as one of the processes describedherein. Alternatively, certain embodiments of the present invention maybe performed entirely in hardware.

FIG. 5B illustrates a system according to certain embodiments. In anexample embodiment, a system may comprise several devices, for exampleMME 510, MSC 520, and BSC/RNC 530. These devices are merely illustrativeof many other devices that can be used, such as the devices shown inFIGS. 2 and 3.

For example, the MME 510 and the MSC 520 may each comprise requestingmeans (respectively 511 and 521) for requesting handover of a userequipment from a source network to a target network and providing means(respectively 513 and 523) for providing a network identificationcorresponding to the source network while requesting the handover. TheBSC/RNC may similarly comprise requesting means 531 for requestinghandover of a user equipment from a source network to a target networkand determining means 533 for determining the target network based on anetwork identification received previously.

The MSC 520 and the BSC/RNC 530 may also comprise forwarding means(respectively 528 and 538) for forwarding a network identificationreceived previously at the source network to the target network. The MSC520 may also comprise receiving means 529 for receiving a request forhandover of a user equipment from a source network to a target network.

The means illustrated in FIG. 5B may be variously implemented, forexample in hardware alone and in software running on hardware. Oneexample of an implementation is illustrated in FIG. 5A, discussed above.

One having ordinary skill in the art will readily understand that theinvention as discussed above may be practiced with steps in a differentorder, and/or with hardware elements in configurations which aredifferent than those which are disclosed. Therefore, although theinvention has been described based upon these preferred embodiments, itwould be apparent to those of skill in the art that certainmodifications, variations, and alternative constructions would beapparent, while remaining within the spirit and scope of the invention.In order to determine the metes and bounds of the invention, therefore,reference should be made to the appended claims.

1. A method, comprising: requesting handover of a user equipment from asource network to a target network; and providing a networkidentification corresponding to the source network while requesting thehandover.
 2. The method of claim 1, wherein the source network comprisesa packet-switched network and the target network comprises a circuitswitched network.
 3. The method of claim 1, wherein the networkidentification comprises an identification of a public land mobilenetwork or a source public land mobile network identifier.
 4. The methodof claim 1, wherein the handover request comprises a packet switched tocircuit switched handover request comprising the network identification,and wherein the handover request comprises a single radio voice callcontinuity request from a packet switched network to a circuit switchednetwork.
 5. (canceled)
 6. The method of claim 1, wherein the requestingthe handover is performed by a mobility management entity or servinggeneral packet radio service support node and the identification isprovided to a mobile switching center. 7-10. (canceled)
 11. The methodof claim 1, wherein handover is requested by the source network andidentification is provided to the target network.
 12. A method,comprising: requesting handover of a user equipment from a sourcenetwork to a target network; and determining the target network based ona network identification received.
 13. The method of claim 12, whereinthe source network comprises a circuit switched network and the targetnetwork comprises a packet switched network.
 14. The method of claim 12,wherein the network identification comprises a source public land mobilenetwork identification from the packet switched network, or a targetpublic land mobile network identifier.
 15. The method of claim 12,wherein the handover request is a circuit switched to packet switchedhandover request comprising the network identification.
 16. The methodof claim 12, wherein the handover comprises a reverse single radio voicecall continuity handover.
 17. The method of claim 12, wherein thehandover request is transmitted from a base station controller or radionetwork controller to a mobile switching center.
 18. The method of claim12, wherein the network identification was received with a packetswitched to circuit switched handover request and is a networkidentification of a used source packet switched public land mobilenetwork. 19-32. (canceled)
 33. An apparatus, comprising: at least oneprocessor; and at least one memory comprising computer program code,wherein at the at least one memory and the computer program code areconfigured to, with the at least one processor, cause the apparatus atleast to request handover of a user equipment from a source network to atarget network; and provide a network identification corresponding tothe source network while requesting the handover.
 34. The apparatus ofclaim 33, wherein the source network comprises a packet-switched networkand the target network comprises a circuit switched network.
 35. Theapparatus of claim 33, wherein the network identification comprises anidentification of a public land mobile network or a source public landmobile network identifier.
 36. The apparatus of claim 33, wherein thehandover request comprises a packet switched to circuit switchedhandover request comprising the network identification, and wherein thehandover request comprises a single radio voice call continuity requestfrom a packet switched network to a circuit switched network. 37.(canceled)
 38. The apparatus of claim 33, wherein the request of thehandover is performed by a mobility management entity or serving generalpacket radio service support node and the identification is provided toa mobile switching center. 39-42. (canceled)
 43. The apparatus of claim33, wherein handover is requested by the source network andidentification is provided to the target network.
 44. The apparatus ofclaim 33, wherein the apparatus comprises a mobility management entityor a mobile switching center.
 45. An apparatus, comprising: at least oneprocessor; and at least one memory comprising computer program code,wherein at the at least one memory and the computer program code areconfigured to, with the at least one processor, cause the apparatus atleast to request handover of a user equipment from a source network to atarget network; and determine the target network based on a networkidentification received.
 46. The apparatus of claim 45, wherein thesource network comprises a circuit switched network and the targetnetwork comprises a packet switched network.
 47. The apparatus of claim45, wherein the network identification comprises a source public landmobile network identification from the packet switched network, or atarget public land mobile network identifier.
 48. The apparatus of claim45, wherein the handover request is a circuit switched to packetswitched handover request comprising the network identification.
 49. Theapparatus of claim 45, wherein the handover comprises a reverse singleradio voice call continuity handover.
 50. The apparatus of claim 45,wherein the handover request is transmitted from a base stationcontroller or radio network controller to a mobile switching center. 51.The apparatus of claim 45, wherein the network identification wasreceived with a packet switched to circuit switched handover request andis a network identification of a used source packet switched public landmobile network.
 52. The apparatus of claim 45, wherein the apparatuscomprises a base station controller or a radio network controller.53-68. (canceled)